System and Method for Entitling Digital Assets

ABSTRACT

A system, method, and computer-readable medium are disclosed for managing the entitlement of digital assets. System identifier data associated with a target system, including its unique system identifier, is received, along with digital assets selection data corresponding to digital assets data to be processed by the target system. The system identifier data is processed with the digital assets selection data to generate digital assets entitlement data. The digital assets data and the digital assets entitlement data is then provided to a personalization agent associated with the target system. In turn, the personalization agent processes the digital assets entitlement data and the digital assets data for installation on the target system, thereby entitling the system to process the installed digital assets data.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to the management of information handlingsystems. More specifically, embodiments of the invention provide asystem, method, and computer-readable medium for managing theentitlement of digital assets.

2. Description of the Related Art

As the value and use of information continues to increase, individualsand businesses seek additional ways to process and store information.One option available to users is information handling systems. Aninformation handling system generally processes, compiles, stores,and/or communicates information or data for business, personal, or otherpurposes thereby allowing users to take advantage of the value of theinformation. Because technology and information handling needs andrequirements vary between different users or applications, informationhandling systems may also vary regarding what information is handled,how the information is handled, how much information is processed,stored, or communicated, and how quickly and efficiently the informationmay be processed, stored, or communicated. The variations in informationhandling systems allow for information handling systems to be general orconfigured for a specific user or specific use such as financialtransaction processing, airline reservations, enterprise data storage,or global communications. In addition, information handling systems mayinclude a variety of hardware and software components that may beconfigured to process, store, and communicate information and mayinclude one or more computer systems, data storage systems, andnetworking systems.

Current approaches to acquiring digital assets on-line, whether inphysical or digital form, typically involve the purchaser placing anorder with on-line retailer and then concluding the purchase with apayment transaction. If the digital assets are in physical form, theyare then shipped to the purchaser. If in digital form, the purchasertypically conducts a download session, which may include a uniquelicense key. Known approaches to managing the licensing of downloadeddigital assets include establishing a license for a digital asset and acorresponding download link such that it can be sent to a particularinformation handling system. The license is then associated with thetarget system and tracked over time for termination, renewal, orpossible transfer to another system.

However, the digital assets may be acquired from multiple on-linesources, including a closed enterprise networking environment, catalogvendors stocking a wide variety of digital assets, or individualsoftware producers. As a result, the purchaser must keep track of thesource for each individual digital asset and its associated license.

Furthermore, it is not uncommon for users to misplace or forget theiruser IDs and passwords. While methods exist to recover a log-in name andpassword, the process is inherently cumbersome and may create delays ininstalling the digital assets on the user's system. In view of theforegoing, there is a need for allowing a broad range of digital assetsto be delivered digitally, through multiple channels, to multipleinformation handling systems, through individual or multiple accounts,and to accommodate various licensing restrictions.

SUMMARY OF THE INVENTION

A system, method, and computer-readable medium are disclosed formanaging the entitlement of digital assets. In various embodiments, adigital assets entitlement system is implemented for managing theentitlement of a target system to process digital assets. In these andother embodiments, the target system comprises a unique systemidentifier, which in turn comprises the unique identifiers ofpredetermined system components.

In various embodiments, the digital assets entitlement receives systemidentifier data associated with the target system, including its uniquesystem identifier, and digital assets selection data corresponding todigital assets data to be processed by the target system. The systemidentifier data is processed with the digital assets selection data togenerate digital assets entitlement data. The digital assets data andthe digital assets entitlement data is then provided to apersonalization agent associated with the target system. In turn, thepersonalization agent processes the digital assets entitlement data andthe digital assets data for installation on the target system, therebyentitling the system to process the installed digital assets data.

In these and other embodiments, the digital assets entitlement data onthe target system allows the target system to process data associatedwith the installed digital assets data. In various embodiments, theunique system identifier comprises a plurality of unique systemcomponent identifiers. In one embodiment, the digital assets entitlementdata comprises user data associated with the unique system identifier.In another embodiment, the digital assets entitlement data comprisesdigital assets license data. In yet another embodiment, the digitalassets data comprises system personalization data.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention may be better understood, and its numerousobjects, features and advantages made apparent to those skilled in theart by referencing the accompanying drawings. The use of the samereference number throughout the several figures designates a like orsimilar element.

FIG. 1 is a general illustration of components of an informationhandling system as implemented in the system and method of the presentinvention;

FIG. 2 is a simplified block diagram of the operation of a digitalassets entitlement system;

FIGS. 3 a-b are a simplified block diagram of a unique system identifierthat remains the same when one of its associated system componentidentifiers has been changed;

FIGS. 4 a-b are a simplified block diagram of a unique system identifierthat is changed when one of its associated system component identifiershas been changed;

FIG. 5 is a simplified block diagram of an encrypted unique systemidentifier generated from a set of system component identifiers;

FIG. 6 is a simplified block diagram of a unique system identifierdecrypted from an encrypted unique system identifier;

FIGS. 7 a-b are a generalized flow chart of the performance of digitalasset entitlement operations; and

FIG. 8 is a generalized flow chart of the performance of digital assetsentitlement and personalization operations in physical and on-lineenvironments.

DETAILED DESCRIPTION

A system, method, and computer-readable medium are disclosed formanaging the entitlement of digital assets. For purposes of thisdisclosure, an information handling system may include anyinstrumentality or aggregate of instrumentalities operable to compute,classify, process, transmit, receive, retrieve, originate, switch,store, display, manifest, detect, record, reproduce, handle, or utilizeany form of information, intelligence, or data for business, scientific,control, or other purposes. For example, an information handling systemmay be a personal computer, a network storage device, or any othersuitable device and may vary in size, shape, performance, functionality,and price. The information handling system may include random accessmemory (RAM), one or more processing resources such as a centralprocessing unit (CPU) or hardware or software control logic, ROM, and/orother types of nonvolatile memory. Additional components of theinformation handling system may include one or more disk drives, one ormore network ports for communicating with external devices as well asvarious input and output (I/O) devices, such as a keyboard, a mouse, anda video display. The information handling system may also include one ormore buses operable to transmit communications between the varioushardware components.

FIG. 1 is a generalized illustration of an information handling system100 that can be used to implement the method and system of the presentinvention. The information handling system 100 includes a processor(e.g., central processor unit or “CPU”) 102, input/output (I/O) devices104, such as a display, a keyboard, a mouse, and associated controllers,a hard drive or disk storage 106, various other subsystems, such as astorage interface 108, a network port 110, and a system memory 112, allinterconnected via one or more buses 114.

FIG. 2 is a simplified block diagram of the operation of a digitalassets entitlement system. In various embodiments, a digital assetsentitlement system 218 is implemented for managing the entitlement of asystem 204 to process a digital asset 246. In these and otherembodiments, the digital assets entitlement system 218 may beimplemented on one or more servers 210, which are connected to a network252. In various embodiments, the network 252 may comprise a publicnetwork, such as the Internet, a physical private network, a virtualprivate network (VPN), or any combination thereof. As shown in FIG. 2,the digital assets entitlement system 218 comprises a user service andsupport module 220, a digital fulfillment module 222, and a systemidentification and security module 224. The digital assets entitlementsystem 218 likewise comprises a personalization module 226, anentitlement module 228, a sales integration module 230, and amanufacturing integration module 232. Likewise, the digital assetsentitlement system 218 is able to access a digital assets datarepository 212, an entitlement data repository 214, and a systemidentifier (ID) data repository 216, each of which may be implemented onone or more servers 210 connected to a network 252.

As used herein, a digital asset 246 refers to any digital asset such asa software application, a deliverable or performable service, music,video, software activation key, personalization instructions, files,etc. that are digitally deliverable either wholly or partially. Aslikewise used herein, a digital assets entitlement refers to theassociation of a predetermined digital asset 246 with a target system204. In various embodiments, an entitlement record contains the digitalassets entitlement data (e.g., license information, etc.) that allowsthe digital asset 246 to be processed by a target system 204 identifiedby a corresponding unique system identifier 206. In these and otherembodiments, the entitlement record is processed by the entitlementmodule 228 and stored in the entitlement data repository 214. Likewise,as used herein, a system 204 may comprise a personal computer, a laptopcomputer, or a tablet computer operable to establish an on-line sessionwith the digital assets entitlement system 218 over a connection tonetwork 252. The system 204 may also comprise a personal digitalassistant (PDA), a mobile telephone, or any other suitable deviceoperable to store a unique system ID 206, perform digital assetentitlement operations with a personalization agent 208, and likewiseoperable to establish a connection with network 252.

In this embodiment, digital assets entitlement and systempersonalization operations are performed by a user, such as a systempurchaser 202, in either a physical environment or an on-lineenvironment. As an example, a physical environment may comprise aretailer 240 operating a physical point-of-sale (POS) system 242. Asanother example, an on-line environment may comprise a systemmanufacturer 234, after-point-of-sale (APOS) vendor 236, or digitalassets vendor 238, that respectively accepts on-line orders for systemsor digital assets over a connection to network 252.

If the digital assets entitlement and system personalization operationsare performed in an on-line environment, then the system purchaser 202decides whether to purchase a custom-configured or pre-configured system204. If the system 204 is to be pre-configured, then it is selected foron-line purchase by the system purchaser 202 and its unique identifier206 is determined. In one embodiment, the unique system identifier 206is stored in the BIOS of the pre-configured system 204. However, if thesystem 204 is to be custom-configured, then it is custom-configured foron-line purchase by the system purchaser 202. Once manufactured by thesystem manufacturer 234, a unique system identifier 206 is generated asdescribed in greater detail herein.

In various embodiments, the manufacturing integration module 232coordinates the pre-configured or custom configured of the system 204with the digital assets entitlement system 218. Likewise, the systemidentification and security module 224 coordinates the generation of theunique system identifier 204 and its storage in the repository of systemidentifier data 216. The system purchaser then selects a digital asset246 for on-line purchase, followed by selecting personalization optionsfor the pre-configured or custom-configured system. In variousembodiments, the personalization module 226 coordinates the selection ofpersonalization options with the digital assets entitlement system 218.As used herein a system personalization option refers to any feature,capability, or function that may be applied to a target system. As anexample, a personal computer desktop wallpaper or user interface options(e.g., a “classic” interface) are personalization options.

However, if the digital assets entitlement and system personalizationoperations are performed in a physical environment, then the systempurchaser 202 selects a pre-configured system 204 and physicalrepresentations of digital assets 246 to be purchased. In variousembodiments, the digital asset 246 is physically represented as imagesand text on a card or a package, yet the digital assets themselves arenot contained within the card or package. The system purchaser 202 thenselects system personalization options for the pre-configured system. Invarious embodiments, the system personalization options are likewisephysically represented as images and text on a card or a package.

The digital assets product identifier (ID) is then scanned with ascanner 244 from its corresponding physical representation, followed byscanning its corresponding digital assets activation key or otherentitlement data. In various embodiments, it is not necessary to scanthe digital assets activation key or other entitlement data as it isprovided by the digital assets entitlement system 218 during digitalasset entitlement operations described in greater detail herein. Datarelated to the previously selected personalization options are thenlikewise scanned, followed by determining the unique system identifier206 of the pre-configured system 204. In various embodiments, thedigital assets product ID, its associated activation key or entitlementdata, the personalization option data, and the unique system identifierare represented by a bar code 248 or other indicia on a card or physicalpackage. In various other embodiments, the digital assets product ID,its associated activation key or entitlement data, the personalizationoption data, and the unique system identifier is contained in a radiofrequency identifier (RFID) 250 tag affixed to the physicalrepresentation of the digital asset. Those of skill in the art willrealize that many such embodiments are possible and that the foregoingis not intended to limit the spirit, scope, or intent of the invention.

A purchase transaction for the custom-configured or pre-configuredsystem 204 and any associated digital assets 246 and personalizationoptions is then completed. In various embodiments, the processing of thepurchase transaction is performed by the sales integration module 230.In these and other embodiments, the financial proceeds of the purchasetransaction may be settled between multiple parties. For example, asystem manufacturer 234 may receive a portion of the purchasetransaction corresponding to the cost of the system 204. One or moredigital assets vendors 238 may likewise receive a proportionate share ofthe purchase transaction corresponding to the digital asset 246 theyrespectively provide.

Digital asset entitlement operations, as described in greater detailherein, are then performed by the digital assets entitlement system 218to bind the digital asset 246, the personalization options, and theirrespective digital assets entitlement data to the unique systemidentifier 206 of the target system 204. The resulting bound data,including data associated with the digital assets (e.g., installationfiles, etc.) is then stored in the repository of entitlement data 214and the purchased system 204 is then delivered to the system purchaser202. In various embodiments, the entitlement module 228 generates, andthen processes, the digital assets entitlement data and the user serviceand support module 220 coordinates the delivery of the system 204 to thesystem purchaser 202.

Standard operating system (OS) out-of-the-box-experience (DOBE) orhypervisor boot operations are performed on the system 204, followed byloading a personalization agent 208. In various embodiments, thepersonalization agent 208 has a unique identifier that is associatedwith one or more unique system component identifiers. In one embodiment,the unique identifier of the personalization agent is uniquelyassociated with the current unique system identifier 206 associated withthe system 204. In another embodiment, a portion of the personalizationagent 208 is delivered to the system 204 in an encrypted form and isthen decrypted prior to being loaded on the system 204. In thisembodiment, the primary system identifier (e.g., service tag number,serial number, etc.), is used as a decryption key to decrypt thepersonalization agent 208.

In various other embodiments, secondary system identifiers are stored onthe system 204 (e.g., in the BIOS, in Flash memory, on a hard disk,etc.) as well as in the digital assets entitlement system 218. In theseand other embodiments, the digital assets entitlement system 218 usesthe secondary system identifiers to encrypt a portion of thepersonalization agent 208 before it is downloaded to the system 204.Once downloaded, the unencrypted portion of the personalization agent208 uses the secondary system identifiers stored on the system 204 todecrypt the encrypted portion of the personalization agent 208. In oneembodiment, the secondary system identifiers are likewise encrypted andare first decrypted before they are used to decrypt the encryptedportion of the personalization agent 208. In another embodiment, theprimary or secondary system identifiers are stored in a Trusted PlatformModule (TPM). Skilled practitioners of the art will recognize that manysuch embodiments are possible and the foregoing is not intended to limitthe spirit, scope, or intent of the invention.

The personalization agent 208 queries the target system for its uniquesystem identifier 206. In various embodiments, the unique systemidentifier 206 associated with the system 204 is stored in the targetsystem's BIOS, flash memory, a hard disk, or other memory device. Thepersonalization agent 208 then automatically establishes a connectionwith the digital assets entitlement system 218 and uses the uniquesystem identifier 206 to authenticate the system 204. The unique systemidentifier 206 is then used by the personalization agent 208 todetermine entitled digital assets and personalization optionscorresponding to the unique system identifier 206.

Once determined, the corresponding personalization options and digitalassets 246, along with their associated digital assets entitlement data,are respectively downloaded to the target system 204 from the repositoryof digital assets 212 and the repository of entitlement data 214. In oneembodiment, the personalization options and digital assets, along withtheir associated digital assets entitlement data, are downloaded from asingle server 210 on the network 252. In another embodiment, thepersonalization options and digital assets are downloaded from one ormore servers 210 on the network 252. In yet another embodiment, thepersonalization options, digital assets, and associated digital assetsentitlement data are respectively downloaded from a plurality of servers210 on a network 252. As an example, a first digital asset 246 may beprovided by the system manufacturer 234 and a second digital asset 246may be provided by a digital assets vendor 238. Likewise, a plurality ofdigital assets 246 may be provided by a corresponding plurality ofdigital assets vendors 238. Skilled practitioners of the art willrealize that many such embodiments and examples are possible and theforegoing is not intended to limit the spirit, scope, or intent of theinvention.

In various embodiments, the digital assets entitlement system 218manages the respective location of the personalization options, digitalassets, and associated digital assets entitlement data to initiate itsprovision. Once downloaded, the personalization agent 208 uses thedigital assets entitlement data to install the digital assets 246 andpersonalization options on the system 204. Thereafter, the systempurchaser 202 may decide to perform an after-point-of-sale (APOS)purchase of a digital asset 246. As used herein, an APOS purchase ofdigital assets refers to any purchase of a digital asset 246 made afterthe initial on-line or physical purchase of the system 204. In variousembodiments, the APOS purchase of a digital asset 246 may be performedin a physical, on-line, or enterprise point-of-sale environment. If theAPOS purchase is performed in an on-line environment, such as from APOSvendor 236, then the system purchaser 202 selects a digital asset 246for on-line purchase. The personalization agent 208 then determines theunique system identifier 206 of the system 204. An APOS purchasetransaction is then performed for purchase of the selected digital asset246. However, if the APOS purchase is performed in a physicalenvironment, then the purchaser selects a physical representation of adigital asset 246 to be purchased. The digital assets product identifier(ID) is then scanned from its corresponding physical representation,followed by scanning its corresponding digital assets activation key orother entitlement data.

Digital asset entitlement operations, as described in greater detailherein, are then performed by the digital assets entitlement system 218to bind the digital asset 246 and their respective digital assetsentitlement data associated with the APOS purchase to the unique systemidentifier 206 of the target system 204. The resulting bound data,including data associated with the digital assets (e.g., installationfiles, etc.) is then stored, as described in greater detail herein, inthe digital assets entitlement system 218. The personalization agent208, as likewise described in greater detail herein, then automaticallyestablishes a connection with the digital assets entitlement system 218,downloads the purchased digital asset 246 and their associated digitalassets entitlement data. Once downloaded, the personalization agent 208then uses the associated digital assets entitlement data to install thedownloaded digital asset 246 on the system 204.

FIGS. 3 a-b are a simplified block diagram of a unique system identifierthat remains the same when one of its associated system componentidentifiers has been changed in accordance with an embodiment of theinvention. As shown in FIG. 3 a, an original unique system identifier320 is generated from a plurality of unique system component identifiers302, which correspond to a plurality of system components contained in atarget system. As likewise shown in FIG. 3 a, the unique systemcomponent identifiers 302 comprise a Model Number 304 ‘SA310J43, aSerial Number 306, sometimes referred to as a service tag number or aprimary system identifier, ‘SEM5239923875’, a Factory ID 308 ‘AUS’, anda Manufacture Date 310 ‘111909’. The unique system component identifiers302 likewise comprise an Original Motherboard ID 314 ‘19374WS238017BH’,a Processor ID 316 ‘92348430-432919237’, a Hard Drive ID 318‘L83747HJ3672’, etc.

As described in greater detail herein, once generated, the originalunique system identifier 320 is associated, such as through a bindingoperation, with predetermined digital assets 332 to generate a digitalassets entitlement 330. As likewise described in greater detail herein,the digital assets entitlement 330 entitles a target system, which isassociated with the original unique system identifier 320, to processthe digital assets 332. However, it is not uncommon for systemcomponents to be replaced due to failure, erratic performance, becomingoutmoded, or for other reasons. It will be appreciated that theentitlement 330 between the original unique system identifier 320 andthe digital assets 332 may be compromised as a result of such areplacement. For example, as illustrated in FIG. 3 b, the OriginalMotherboard ID 314 ‘19374WS238017BH’ has been replaced with a NewMotherboard ID 334 ‘56812FR853945PL’. However, the original uniquesystem identifier 320 remains unchanged.

In various embodiments, extract, transform, and load (ETL) and otherdatabase operations are performed to manage the integrity of therelationship between the original unique system identifier 320 and theplurality of unique system component identifiers 302. As an example, theOriginal Motherboard ID 314 ‘19374WS238017BH’ may remain as a subset ofthe original unique system identifier 320, even though it may have beendeactivated or invalidated as a unique system component identifier 302.However, in these and other embodiments, relational database operationsknown to those of skill in the art may be applied to maintain therelationship between the original unique system identifier 320, the NewOriginal Motherboard ID 334 ‘56812FR853945PL’, and the unchanged uniquesystem component identifiers 302. Accordingly, the integrity of theentitlement 330 between the original unique system identifier 320 andthe digital assets 332 is perpetuated. It will be apparent to skilledpractitioners of the art that many such embodiments are possible and theforegoing is not intended to limit the spirit, scope, or intent of theinvention.

FIGS. 4 a-b are a simplified block diagram of a unique system identifierthat is changed when one of its associated system component identifiershas been changed in accordance with an embodiment of the invention. Asshown in FIG. 4 a, an original unique system identifier 320 is generatedfrom a plurality of unique system component identifiers 302, whichcorrespond to a plurality of system components contained in a targetsystem. As likewise shown in FIG. 3 a, the unique system componentidentifiers 302 comprise a Model Number 304 ‘SA310J43, a Serial Number306, sometimes referred to as a service tag number or a primary systemidentifier, ‘SEM5239923875’, a Factory ID 308 ‘AUS’, and a ManufactureDate 310 ‘111909’. The unique system component identifiers 302 likewisecomprise an Original Motherboard ID 314 ‘19374WS238017BH’, a ProcessorID 316 ‘92348430-432919237’, a Hard Drive ID 318 ‘L83747HJ3672’, etc.

As described in greater detail herein, once generated, the originalunique system identifier 320 is associated, such as through a bindingoperation, with predetermined digital assets 332 to generate a digitalassets entitlement 330. As likewise described in greater detail herein,the digital assets entitlement 330 entitles a target system, which isassociated with the original unique system identifier 320, to processthe digital assets 332. However, it is not uncommon for systemcomponents to be replaced due to failure, erratic performance, becomingoutmoded, or for other reasons. It will be appreciated that theentitlement 330 between the original unique system identifier 320 andthe digital assets 332 may be compromised as a result of such areplacement. For example, as illustrated in FIG. 4 b, the OriginalMotherboard ID 314 ‘19374WS238017BH’ has been replaced with a NewMotherboard ID 334 ‘56812FR853945PL’. As a result, a new unique systemidentifier 420 is generated, which is a concatenation of the pluralityof unique system component identifiers 402, including the New OriginalMotherboard ID 334 ‘56812FR853945PL’ as a subset.

In various embodiments, a first set of operations are performed toremove the entitlement 330 between the original unique system identifier320 and digital assets 332. A second set of operations are thenperformed to associate the new unique system identifier 420 with thedigital assets 332 to generate a new entitlement 430. In these and otherembodiments, the original unique system identifier 320 is theninvalidated. Accordingly, the integrity of the original entitlement 330between the original unique system identifier 320 and the digital assets332 is perpetuated by the new entitlement 430 between the new uniquesystem identifier 420 and the digital assets 332. Skilled practitionersof the art will recognize that many such embodiments are possible andthe foregoing is not intended to limit the spirit, scope, or intent ofthe invention.

FIG. 5 is a simplified block diagram of an encrypted unique systemidentifier generated from a set of system component identifiers inaccordance with an embodiment of the invention. In this embodiment, asource unique system identifier 520 is generated from a plurality oforiginal unique system component identifiers 502, which correspond to aplurality of system components contained in a target system. As shown inFIG. 5, the original unique system component identifiers 502 comprise aModel Number 304 ‘SA310J43, a Serial Number 306, sometimes referred toas a service tag number or a primary system identifier, ‘SEM5239923875’,a Factory ID 308 ‘AUS’, a Timestamp Date 510 ‘111909’, and a TimestampTime 512 ‘14:27:26:34’. The original unique system component identifiers502 likewise comprise an Original Motherboard ID 314 ‘19374WS238017BH’,a Processor ID 316 ‘92348430-432919237’, a Hard Drive ID 318‘L83747HJ3672’, etc.

An encryption operation 524 is then performed on the source uniquesystem identifier 520 to generate an original encrypted unique systemidentifier 528. In various embodiments, the encryption operation maycomprise the use of a private key, a public key, key pairs, or anycombination of keys and cryptographic operations such as implemented ina public key infrastructure (PKI). As an example, the original encryptedunique system identifier 528 may be generated using a private keyassociated with the manufacturer of the system and a public keyassociated with the system itself. In one embodiment, the Timestamp Date510 ‘111909’ and the Timestamp Time 512 ‘14:27:26:34’ are likewise usedto generate the encrypted unique system identifier 528. Skilledpractitioners of the art will be familiar with such cryptographicoperations and recognize that many such embodiments are possible andthat the foregoing is not intended to limit the spirit, scope, or intentof the invention.

As described in greater detail herein, once generated, the originalencrypted unique system identifier 528 is associated, such as through abinding operation, with predetermined digital assets 332 to generate adigital assets entitlement 530. As likewise described in greater detailherein, the digital assets entitlement 530 entitles a target system,which is associated with the original encrypted unique system identifier528, to process the digital assets 332.

FIG. 6 is a simplified block diagram of a unique system identifierdecrypted from an encrypted unique system identifier in accordance withan embodiment of the invention. It is not uncommon for system componentsto be replaced due to failure, erratic performance, becoming outmoded,or for other reasons. However, the replaced system component willtypically have a different unique system component identifier. As aresult, the entitlement association between a unique system identifierand predetermined digital assets may be compromised as a result of sucha replacement, which in turn may prevent the target system fromprocessing the digital assets.

In various embodiments, the unique system component identifier of thereplacement system component is unknown until it is replaced in thetarget system. In these and other embodiments, the system component isreplaced in the target system, the target system is then initiated(e.g., booted), and an inventory of unique system component identifiersis performed. In one embodiment, one or more unique system componentidentifiers, such as a serial number or service tag, are visible and maybe visually inventoried. In another embodiment, one or more uniquesystem component identifiers, such as a motherboard, processor, or harddrive serial number, are not visible and may be automaticallyinventoried.

As shown in FIG. 6, a new source unique system identifier 650 isgenerated from the inventoried unique system component identifiers. Inone embodiment, a time stamp date and a time stamp time are componentsof the new source unique system identifier 650. In this embodiment, thetime stamp date and a time stamp time are used to validate theauthenticity of the new source unique system identifier 650. As anexample, the provider of the replacement part may have stipulated thatthe replacement part be replaced on November 12th, 2009, between 8:00 AMand 6:00 PM. Accordingly, a time state date of November 12th, 2009 and atime stamp time of 16:33:42:05 would provide validation that thereplacement part was replaced within the specified date and timeinterval.

An encryption operation 652 is then performed on the new source uniquesystem identifier 650 to generate a new encrypted unique systemidentifier 628. As an example, the encryption operation may be performedusing a private key associated with the target system and a public keyassociated with the provider of the replacement system component. Thenew encrypted unique system identifier 628 is then communicated to adigital assets entitlement system, which in turn performs a decryptionoperation 626 to generate a decrypted unique system identifier 622.

As likewise shown in FIG. 6, extract, transform, and load (ETL) andother database operations 634 are performed on the decrypted uniquesystem identifier 622 to generate new unique system componentidentifiers 602. As shown in FIG. 6, the new unique system componentidentifiers now comprise a Model Number 304 ‘SA310J43, a Serial Number306, ‘SEM5239923875’, a Factory ID 308 ‘AUS’, a Timestamp Date 610‘112009’, and a Timestamp Time 612 ‘16:33:42:05’. The new unique systemcomponent identifiers 602 likewise comprise a New Motherboard ID 314‘56812FR853945PL’, a Processor ID 316 ‘92348430-432919237’, a Hard DriveID 318 ‘L83747HJ3672’, etc. In one embodiment, the Timestamp Date 610and the Timestamp Time 612 are compared to previously authorizedtimestamp date and timestamp times to validate the authenticity of thenew unique system component identifiers 602 and their correspondingdecrypted unique system identifier 622. In this and other embodiments,if the decrypted unique system identifier 622 is validated, then a firstset of operations are performed to remove the entitlement between theoriginal encrypted unique system identifier and digital assets 332. Asecond set of operations are then performed to associate the newencrypted unique system identifier 628 with the digital assets 332 togenerate a new entitlement 630. Accordingly, the integrity of theoriginal entitlement between the original encrypted unique systemidentifier and the digital assets 332 is perpetuated by the newentitlement 630 between the new encrypted unique system identifier 628and the digital assets 332.

In various other embodiments, the provider of the replacement systemcomponent is able to determine its associated unique system componentidentifier. In one embodiment, the unique system component identifier isknown in advance. In another embodiment, the unique system componentidentifier may be one of a pool of, or a range of, possible uniquesystem component identifiers set aside for replacement purposes. Asdescribed in greater detail herein, a new source unique identifier isgenerated, using the unique system component identifier of the componentto be replaced. Once the new source unique identifier is generated theunique system component identifier of the replaced system component isinvalidated. In these and other embodiments, the system component isreplaced in the target system, the target system is then initiated(e.g., booted), and an inventory of unique system component identifiersis performed. In one embodiment, one or more unique system componentidentifiers, such as a serial number or service tag, are visible and maybe visually inventoried. In another embodiment, one or more uniquesystem component identifiers, such as a motherboard, processor, or harddrive serial number, are not visible and may be automaticallyinventoried.

As shown in FIG. 6, a new source unique system identifier 650 isgenerated from the inventoried unique system component identifiers. Inone embodiment, a time stamp date and a time stamp time are componentsof the new source unique system identifier 650. In this embodiment, thetime stamp date and a time stamp time are used to validate theauthenticity of the new source unique system identifier 650. Anencryption operation 652 is then performed on the new source uniquesystem identifier 650 to generate a new encrypted unique systemidentifier 628. As an example, the encryption operation may be performedusing a private key associated with the target system and a public keyassociated with the provider of the replacement system component. Thenew encrypted unique system identifier 628 is then communicated to adigital assets entitlement system, which in turn performs a decryptionoperation 626 to generate a decrypted unique system identifier 622.

Comparison operations 654 are then performed between the new sourceunique system identifier and the decrypted unique system identifier 622.If the comparison operations 654 are successful, then a first set ofoperations are performed to remove the entitlement between the originalencrypted unique system identifier and digital assets 332. A second setof operations are then performed to associate the new encrypted uniquesystem identifier 628 with the digital assets 332 to generate a newentitlement 630. Accordingly, the integrity of the original entitlementbetween the original encrypted unique system identifier and the digitalassets 332 is perpetuated by the new entitlement 630 between the newencrypted unique system identifier 628 and the digital assets 332.Skilled practitioners of the art will recognize that many suchembodiments are possible and the foregoing is not intended to limit thespirit, scope, or intent of the invention.

FIGS. 7 a-b are a generalized flow chart of the performance of digitalasset entitlement operations in an embodiment of the invention, In thisembodiment, digital asset entitlement operations are started in step702, followed by the selection of a target system in step 704 fordigital assets entitlement. The unique system identifier of the targetsystem, as described in greater detail herein, is determined in step706, followed by a determination being made in step 708 whether a devicerecord has been established for the target system. If not, then thedevice record is generated in step 710. As used herein, a device recordrefers to a data record containing data related to a system which willreceive an entitlement to process associated digital assets. In variousembodiments, the unique system identifier of the target system is storedin the device record. In various embodiments, other records may beassociated with the device record to further describe the system, suchas its model, type, make, internal identifiers, etc.

Once the device record has been generated, or if it is determined instep 708 that it has already been established, then a determination ismade in step 712 whether an account record has been established for auser. If not, then the account record is generated for the user in step714. As used herein, an account record refers to a data recordcontaining data related to the association of multiple devices orsystems to one or more entities. In various embodiments, the entity maybe a single individual or a group of individuals. As an example, theentity may be a household with multiple PCs, a small business withseveral employees, a large corporation with many employees, etc. Otherrecords may be attached to the account to further describe the accountholder, payment information related to the account, etc. Accounts mayfurther be broken down or organized into sub-accounts as needed, such asto describe departments within an enterprise). In various embodiments, auser may be associated with a single device or system or multipledevices or systems in the account record. Conversely, a group of usersmay be associated with a single device or system or multiple devices inthe account record. Further more groups of individual users may likewisebe associated with groups of individual devices or systems. Those ofskill in the art will recognize that many such associations are possibleand the foregoing is not intended to limit the spirit, scope, or intentof the invention. Once the account record has been generated, or if itis determined in step 712 that it has already been established, then adetermination is made in step 716 whether the account record isassociated with the target system. If not, then the account record isassociated with the target system in step 718.

Once the account record has been associated with the target system, orif it is determined in step 716 that it has already been associated,then a target list of digital assets is presented in step 720 forentitlement. A determination is then made in step 722 whether togenerate an entitlement for a digital asset. If not, then adetermination is made in step 732 whether to continue digital assetentitlement operations. If so, then the process is continued, proceedingwith step 704. Otherwise digital asset entitlement operations are endedin step 734. However, if it is determined in step 722 to generate anentitlement for a digital asset, then a target digital asset is selectedin step 726. A digital assets entitlement is then generated in step 726by performing operations to associate the selected digital asset'scorresponding license record with the aforementioned device record,account record, and other predetermined records. The resulting digitalassets entitlement association is then added to the entitlement recordin step 728. A determination is then made in step 730 whether togenerate another digital assets entitlement. If so, the process iscontinued, proceeding with step 724. Otherwise, a determination is madein step 732 whether to continue digital asset entitlement operations. Ifso, then the process is continued, proceeding with step 704. Otherwisedigital asset entitlement operations are ended in step 734.

FIG. 8 is a generalized flow chart of the performance of digital assetsentitlement and system personalization operations in physical andon-line environments as implemented in an embodiment of the invention.In this embodiment, digital assets entitlement and systempersonalization operations are begun by a system purchaser in step 802,followed by a determination being made in step 804 whether theentitlement and system personalization operations are performed in aphysical environment or an on-line environment. If it is determined instep 804 that the digital assets entitlement and system personalizationoperations are performed in an on-line environment, then a determinationis made in step 806 whether the target system is to be custom-configuredor pre-configured. If it is determined in step 806 that the targetsystem is to be a pre-configured system, then the system purchaserselects the target system for on-line purchase in step 808. The uniqueidentifier for the selected pre-configured system is then determined instep 810. In one embodiment, the unique system identifier is stored inthe BIOS of the pre-configured target system.

However, if it is determined in step 806 that the target system is to bea custom-configured system, then the system purchaser configures thetarget system for on-line purchase in step 812. The target system isthen manufactured in step 814 according to the custom configurationselections made by the purchaser in step 812. Once manufactured, aunique system identifier is generated in step 816, as described ingreater detail herein. Then, or after the unique system identifier isdetermined for the pre-configured system in step 810, the systempurchaser selects digital assets for on-line purchase in step 818,followed by selecting personalization options for the custom-configuredsystem in step 820.

However, if it is determined in step 804 that the entitlement and systempersonalization operations are to be performed in a physicalenvironment, then the system purchaser selects a pre-configured systemin step 822 to purchase. The system purchaser then selects a physicalrepresentation of digital assets to be purchased in step 824. In variousembodiments, the digital assets are physically represented as images andtext on a card or a package, yet the digital assets themselves are notcontained within the card or package. The system purchaser then selectssystem personalization options for the pre-configured system in step826. In various embodiments, the system personalization options arephysically represented as images and text on a card or a package.

The digital assets product identifier (ID) is then scanned from itscorresponding physical representation in step 828, followed by scanningits corresponding digital assets activation key or other entitlementdata in step 830. Data related to the previously selectedpersonalization options are then likewise scanned in step 832, followedby determining the unique system identifier of the pre-configured systemin step 834. In various embodiments, the digital assets product ID, itsassociated activation key or entitlement data, the personalizationoption data, and the unique system identifier are represented by a barcode or other indicia on a card or physical package. In various otherembodiments, the digital assets product ID, its associated activationkey or entitlement data, the personalization option data, and the uniquesystem identifier is contained in a radio frequency identifier (RFID)tag affixed to the physical representation of the digital asset. Thoseof skill in the art will realize that many such embodiments are possibleand that the foregoing is not intended to limit the spirit, scope, orintent of the invention.

Once the system personalization data has been provided in step 820, orthe unique system identifier has been determined in step 834, a purchasetransaction for the custom-configured or pre-configured target systemand any associated digital assets and personalization options iscompleted in step 836. Digital asset entitlement operations, asdescribed in greater detail herein, are then performed by a digitalassets entitlement system in step 838 to bind the digital assets, thepersonalization options, and their respective digital assets entitlementdata to the unique system identifier of the target system. The resultingbound data, including data associated with the digital assets (e.g.,installation files, etc.) is then stored in the digital assetsentitlement system in step 840 and the custom-configured orpre-configured system is then delivered to the system purchaser in step842.

Standard operating system (OS) out-of-the-box-experience (DOBE) orhypervisor boot operations are performed on the new target system instep 844, followed by loading a personalization agent on the targetsystem in step 846. In various embodiments, the personalization agenthas a unique identifier that is associated with one or more uniquesystem component identifiers. In one embodiment, the unique identifierof the personalization agent is uniquely associated with the currentunique system identifier associated with the target system. In anotherembodiment, a portion of the personalization agent is delivered to thetarget system in an encrypted form and is then decrypted prior to beingloaded on the target system. In this embodiment, the primary systemidentifier (e.g., service tag number, serial number, etc.), is used as adecryption key to decrypt the personalization agent.

In various other embodiments, secondary system identifiers are stored onthe target system (e.g., in the BIOS, in Flash memory, on a hard disk,etc.) as well as in the digital assets entitlement system. In these andother embodiments, the digital assets entitlement system uses thesecondary system identifiers to encrypt a portion of the personalizationagent before it is downloaded to the target system. Once downloaded, theunencrypted portion of the personalization agent uses the secondarysystem identifiers stored on the target system to decrypt the encryptedportion of the personalization agent. In one embodiment, the secondarysystem identifiers are likewise encrypted and are first decrypted beforethey are used to decrypt the encrypted portion of the personalizationagent. In another embodiment, the secondary system identifiers arestored in a Trusted Platform Module (TPM). In yet another embodiment,primary system identifiers are stored in a TPM. Skilled practitioners ofthe art will recognize that many such embodiments are possible and theforegoing is not intended to limit the spirit, scope, or intent of theinvention.

The personalization agent then queries the target system for its uniquesystem identifier in step 848. In various embodiments, the unique systemidentifier associated with the target system is stored in the targetsystem's BIOS, flash memory, a hard disk, or other memory device. Thepersonalization agent then automatically establishes a connection withthe digital assets entitlement system in step 850 and uses the uniquesystem identifier to authenticate the system. Then, in step 852, theunique system identifier is used by the personalization agent in anelectronic interchange with a digital assets entitlement system todetermine entitled digital assets and personalization optionscorresponding to the unique system identifier.

Once determined, the corresponding personalization options and digitalassets, along with their associated digital assets entitlement data, aredownloaded in step 854 to the target system. In one embodiment, thepersonalization options and digital assets, along with their associateddigital assets entitlement data, are downloaded from a single server ona network. In another embodiment, the personalization options anddigital assets are downloaded from one or more servers on a network. Inyet another embodiment, the personalization options, digital assets, andassociated digital assets entitlement data are respectively downloadedfrom a plurality of servers on a network. In these and otherembodiments, the digital assets entitlement system manages therespective location of the personalization options, digital assets, andassociated digital assets entitlement data to initiate its provision.Once downloaded, the personalization agent uses the digital assetsentitlement data in step 856 to install the digital assets andpersonalization options on the target system.

A determination is then made in step 858 whether to perform anafter-point-of-sale (APOS) purchase of digital assets. If it isdetermined in step 858 to not perform an APOS purchase of digitalassets, then a determination is made in step 884 whether to continuedigital assets entitlement and system personalization operations. If so,then the process is continued, proceeding with step 856. Otherwise,digital assets entitlement and system personalization operations areended in step 886.

However, if it is determined in step 858 to perform an APOS purchase ofdigital assets, then a determination is made in step 860 whether theAPOS purchase will be performed in an on-line or physical environment.If it is determined in step 860 that the APOS purchase is to beperformed in an on-line environment, then the purchaser selects digitalassets in step 862 to purchase on-line. The purchaser then likewiseselects any personalization options to purchase on-line in step in step864. The personalization agent then determines the unique systemidentifier of the target system in step 874, followed by performing anAPOS purchase transaction in step 876 for the purchase of the digitalassets and personalization options.

Digital asset entitlement operations, as described in greater detailherein, are then performed by the digital assets entitlement system instep 880 to bind the digital assets, the personalization options, andtheir respective digital assets entitlement data associated with theAPOS purchase to the unique system identifier of the target system. Theresulting bound data, including data associated with the digital assets(e.g., installation files, etc.) is then stored in the digital assetsentitlement system in step 882. The process is then continued,proceeding with step 848.

However, if it was determined in step 860 that the APOS purchase is tobe performed in a physical environment, then the purchaser selects aphysical representation of digital assets to be purchased in step 866.The digital assets product identifier (ID) is then scanned from itscorresponding physical representation in step 868, followed by scanningits corresponding digital assets activation key or other entitlementdata in step 870. The system purchaser then selects systempersonalization options, which are likewise scanned in step 872. Theprocess is then continued, proceeding with step 874.

The present invention is well adapted to attain the advantages mentionedas well as others inherent therein. While the present invention has beendepicted, described, and is defined by reference to particularembodiments of the invention, such references do not imply a limitationon the invention, and no such limitation is to be inferred. Theinvention is capable of considerable modification, alteration, andequivalents in form and function, as will occur to those ordinarilyskilled in the pertinent arts. The depicted and described embodimentsare examples only, and are not exhaustive of the scope of the invention.

For example, the above-discussed embodiments include software modulesthat perform certain tasks. The software modules discussed herein mayinclude script, batch, or other executable files. The software modulesmay be stored on a machine-readable or computer-readable storage mediumsuch as a disk drive. Storage devices used for storing software modulesin accordance with an embodiment of the invention may be magnetic floppydisks, hard disks, or optical discs such as CD-ROMs or CD-Rs, forexample. A storage device used for storing firmware or hardware modulesin accordance with an embodiment of the invention may also include asemiconductor-based memory, which may be permanently, removably orremotely coupled to a microprocessor/memory system. Thus, the modulesmay be stored within a computer system memory to configure the computersystem to perform the functions of the module. Other new and varioustypes of computer-readable storage media may be used to store themodules discussed herein. Additionally, those skilled in the art willrecognize that the separation of functionality into modules is forillustrative purposes. Alternative embodiments may merge thefunctionality of multiple modules into a single module or may impose analternate decomposition of functionality of modules. For example, asoftware module for calling sub-modules may be decomposed so that eachsub-module performs its function and passes control directly to anothersub-module.

Consequently, the invention is intended to be limited only by the spiritand scope of the appended claims, giving full cognizance to equivalentsin all respects.

1. A system for managing the entitlement of digital assets, comprising:a storage medium comprising a repository of system identifier data,digital assets data, and digital assets entitlement data; and aprocessor, the processor being operable to: receive input datacomprising system identifier data associated with a target system;receive input data comprising digital assets selection data, wherein thedigital assets selection data corresponds to digital assets data;process the input data to generate digital assets entitlement data,wherein the digital assets entitlement data is associated with thetarget system identified by the system identifier data and with digitalassets corresponding to the digital assets selection data; and providethe digital assets data and the digital assets entitlement data to apersonalization agent associated with the target system, wherein thepersonalization agent processes the digital assets entitlement data andthe digital assets data for installation on the target system.
 2. Thesystem of claim 1, wherein the installation of the digital assetsentitlement data on the target system allows the target system toprocess data associated with the installed digital assets data.
 3. Thesystem of claim 1, wherein the unique system identifier comprises aplurality of unique system component identifiers.
 4. The system of claim1, wherein the digital assets entitlement data comprises user dataassociated with the unique system identifier.
 5. The system of claim 1,wherein the digital assets entitlement data comprises digital assetslicense data.
 6. The system of claim 1, wherein the digital assets datacomprises system personalization data.
 7. A computer-implemented methodfor managing the entitlement of digital assets, comprising: receivinginput data comprising system identifier data associated with a targetsystem; receiving input data comprising digital assets selection data,wherein the digital assets selection data corresponds to digital assetsdata; processing the input data to generate digital assets entitlementdata, wherein the digital assets entitlement data is associated with thetarget system identified by the system identifier data and with digitalassets corresponding to the digital assets selection data; and providingthe digital assets data and the digital assets entitlement data to apersonalization agent associated with the target system, wherein thepersonalization agent processes the digital assets entitlement data andthe digital assets data for installation on the target system.
 8. Themethod of claim 7, wherein the installation of the digital assetsentitlement data on the target system allows the target system toprocess data associated with the installed digital assets data.
 9. Themethod of claim 7, wherein the unique system identifier comprises aplurality of unique system component identifiers.
 10. The method ofclaim 7, wherein the digital assets entitlement data comprises user dataassociated with the unique system identifier.
 11. The method of claim 7,wherein the digital assets entitlement data comprises digital assetslicense data.
 12. The method of claim 7, wherein the digital assets datacomprises system personalization data.
 13. A computer-usable mediumembodying computer program code, the computer program code comprisingcomputer executable instructions configured for: using a storage mediumcomprising a repository of system identifier data, digital assets data,and digital assets entitlement data; and using processing logic to:receive input data comprising system identifier data associated with atarget system; receive input data comprising digital assets selectiondata, wherein the digital assets selection data corresponds to digitalassets data; process the input data to generate digital assetsentitlement data, wherein the digital assets entitlement data isassociated with the target system identified by the system identifierdata and with digital assets corresponding to the digital assetsselection data; and provide the digital assets data and the digitalassets entitlement data to a personalization agent associated with thetarget system, wherein the personalization agent processes the digitalassets entitlement data and the digital assets data for installation onthe target system.
 14. The computer usable medium of claim 13, whereinthe installation of the digital assets entitlement data on the targetsystem allows the target system to process data associated with theinstalled digital assets data.
 15. The computer usable medium of claim13, wherein the unique system identifier comprises a plurality of uniquesystem component identifiers.
 16. The computer usable medium of claim13, wherein the digital assets entitlement data comprises user dataassociated with the unique system identifier.
 17. The computer usablemedium of claim 13, wherein the digital assets entitlement datacomprises digital assets license data.
 18. The computer usable medium ofclaim 13, wherein the digital assets data comprises systempersonalization data.
 19. The computer usable medium of claim 13,wherein the computer executable instructions are deployable to a clientcomputer from a server at a remote location.
 20. The computer usablemedium of claim 13, wherein the computer executable instructions areprovided by a service provider to a customer on an on-demand basis.